chore: release main - #479
Merged
deepthi-rao-scale merged 2 commits intoJul 29, 2026
Merged
Conversation
…le local tag (#478) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
deepthi-rao-scale
enabled auto-merge (squash)
July 29, 2026 23:24
deepthi-rao-scale
approved these changes
Jul 29, 2026
deepthi-rao-scale
deleted the
release-please--branches--main--changes--next
branch
July 29, 2026 23:27
Contributor
Author
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
✨ Stainless prepared a new release
agentex-client: 0.22.1
0.22.1 (2026-07-29)
Full Changelog: agentex-client-v0.22.0...agentex-client-v0.22.1
Bug Fixes
agentex-sdk: 0.22.1
0.22.1 (2026-07-29)
Full Changelog: agentex-sdk-v0.22.0...agentex-sdk-v0.22.1
Chores
This pull request is managed by Stainless's GitHub App.
The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.
🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions
Greptile Summary
This patch release (0.22.0 → 0.22.1) fixes a CI bug where
docker pushwas re-pushing a stale local tag instead of the freshly built multi-platform image — multi-arch buildx outputs cannot be loaded into the local Docker store, so any subsequentdocker pushwould have sent the wrong image.--pushflag on the build step), the image is validated from the registry, then promoted to:latestviadocker buildx imagetools create(a registry-side manifest copy that preserves the multi-arch manifest list without rebuilding).agentex agents buildandbuild_agent()now defaultcache=Trueinstead ofFalse; the old default's rationale (preventing stale layers when republishing a moving:latesttag) no longer applies since the workflow now uses immutable SHA tags for the candidate before promotion.agentex-clientandagentex-sdkboth increment to 0.22.1 with updated changelogs and manifests.Confidence Score: 5/5
Safe to merge — the CI workflow is well-structured and the new push-from-buildx pattern correctly avoids the multi-platform image problem that the old approach had.
The workflow change is sound: the candidate SHA tag is pushed directly by buildx, validated from the registry, then promoted to :latest via a registry-side copy. No rebuild occurs at the promotion step, and :latest is never touched if validation fails. The cache default flip in the CLI is intentional and consistent with the new immutable-tag build strategy. All other changes are version bumps and changelog entries.
Files Needing Attention: No files require special attention. The GitHub Actions workflow is the most substantive change and the logic is straightforward.
Important Files Changed
Sequence Diagram
sequenceDiagram participant GHA as GitHub Actions participant Buildx as docker buildx participant Registry as Container Registry participant Validator as Validate Step GHA->>Buildx: agentex agents build --push (SHA tag) Buildx->>Registry: Push multi-platform manifest to :sha GHA->>Validator: "Validate image (FULL_IMAGE=:sha)" Validator->>Registry: "Pull & inspect :sha" Validator-->>GHA: All checks passed GHA->>Registry: imagetools create --tag :latest :sha Note over Registry: :latest now points to validated :shaReviews (1): Last reviewed commit: "chore: release main" | Re-trigger Greptile